Providing gesture functionality

ABSTRACT

Gesture functionality is provided in a computing environment. In example embodiments, a gesture input is received. A style difference is identified between a known gesture input of a set of known gesture inputs and the received gesture input. The set of known gesture inputs is caused to be modified to include the style difference by updating a database that stores the set of known gesture inputs.

RELATED APPLICATIONS

The present application is a continuation of and claims priority to U.S.patent application Ser. No. 16/165,790, filed Oct. 19, 2018, which is acontinuation of and claims priority to U.S. patent application Ser. No.15/214,233, filed Jul. 19, 2016, which is a continuation of and claimspriority to U.S. patent Ser. No. 12/559,409, filed Sep. 14, 2009, whichapplication claims the priority benefit of U.S. Provisional PatentApplication No. 61/155,097, filed Feb. 24, 2009 and entitled “Systemsand Method for Receiving a Gesture Input at a Mobile Device.” Thecontent of the aforementioned applications is incorporated in itsentirety herein by reference.

BACKGROUND

Computing devices including mobile devices have become increasingpopular. These computing devices are capable of executing instructionsbased on conventional inputs such cursor inputs or keyboard inputs. Insome instances, the ability to provide quicker more intuitive inputs maybe desired.

BRIEF DESCRIPTION OF DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present invention and cannot be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating an example embodiment of anetwork architecture of a system used to allow multi-directional visualbrowsing.

FIG. 2 is a block diagram illustrating an example embodiment of apublication system.

FIG. 3 is a block diagram illustrating an example embodiment of agesture engine.

FIG. 4 is a block diagram illustrating an example embodiment of anexecution engine.

FIG. 5 is a flowchart illustrating a method to provide gesture functionsat a device.

FIG. 6a and FIG. 6b illustrate an example of a gesture input at a clientdevice.

FIG. 7a and FIG. 7b illustrate other examples of gesture inputs at theclient device.

FIG. 8 is a simplified block diagram of a machine in an example form ofa computing system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the present invention. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques have not been shown in detail.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Additionally, although various example embodimentsdiscussed below focus on a network-based marketplace environment, theembodiments are given merely for clarity in disclosure. Thus, any typeof electronic commerce or electronic business system and method,including various system architectures, may employ various embodimentsof the gesture input system and method described herein and isconsidered as being within a scope of example embodiments. Each of avariety of example embodiments is discussed in detail, below.

Example embodiments described herein provide systems and methods forproviding gesture functionality at a device. In example embodiments, agesture input is received. The gesture input represents acommerce-related action, whereby the commerce-related action is to beperformed on a networked environment. The gesture input may comprisecoordinates associated with the commerce-related action. Furthermore,the gesture input may represent various symbols, such as letters (e.g.,B, S, W, P), which represent various commerce-related actions (e.g., abuy commerce-related action, a sell commerce-related action, a watchcommerce-related action, or a pay commerce-related action). The gestureinput may be received with motion performed relative to a user interfaceof a device or a motion performed with the device itself, whereby themotion may represent a commerce-related action (e.g., update and refreshcommerce-related action).

A determination may be performed to determine that the commerce-relatedaction is executable (e.g., can be performed based on an associatedstatus). The commerce-related action is then performed based on thedetermination that the commerce-related action is executable. In exampleembodiments, performing the commerce-related action comprises performinga commerce-related transaction on the networked environment.

With reference to FIG. 1, an example embodiment of a high-levelclient-server-based network architecture 100 to provide gesturefunctions at a device is shown. A networked system 102, in an exampleform of a network-server-side functionality, is coupled via a network104 (e.g., the Internet or Wide Area Network (WAN)) to one or moreclients. FIG. 1 illustrates, for example, a web client 106 operating viaa browser (e.g., such as the INTERNET EXPLORE® browser developed byMicrosoft® Corporation of Redmond, Wash. State) and a programmaticclient 108 executing on, respectively, client devices 110 and 112. Theclient devices 110 and 112 may include, for example, a mobile phone, apersonal digital assistant (PDA), a gaming unit, a portable computingunit, or any other device capable of being communicatively coupled tothe network 104.

The network 104 over which the networked system 102 and the clientdevices 110 and 112 interact may be a Global System for MobileCommunications (GSM) network, an Internet Protocol (IP) network, aWireless Application Protocol (WAP) network, a WiFi network, or a IEEE802.11 standards network as well as various combinations thereof. Otherconventional and/or later developed wired and wireless networks may alsobe used.

An Application Program Interface (API) server 114 and a web server 116are coupled to, and provide programmatic and web interfaces respectivelyto, one or more application servers 118. The application servers 118host a publication system 120 (e.g., a marketplace system or commercesystem) and a payment system 122, each of which may comprise one or moremodules, applications, or engines, and each of which may be embodied ashardware, software, firmware, or any combination thereof. Theapplication servers 118 are, in turn, coupled to one or more databaseservers 124 facilitating access to one or more information storagedatabases or repositories 126.

The databases 126 includes a collection of data comprising item images,transaction data, and item attribute information. The item images may beimages used in an item listing to show a picture of the item. The itemimages may also be used for comparison with the image data received fromthe client device 110 or 112. The transaction data may includeinformation regarding transactions conducted on the networked system102. The transactional data may include, by way of example, pricinginformation for an item during a time period. The item attributeinformation may include information associate with an item including,for example, an image, title, subtitle, category, sub-category, relateditem listings, average price, quantities of the item currentlyavailable, and any other data that may describe and distinguish the itemfrom other items in the database 126 or other items offered using thenetworked system 102.

The publication system 120 provides a number of functions and servicesto users that access the networked system 102. The publication system120 is discussed in more detail in connection with FIG. 2.

The payment system 122 provides a number of payment services andfunctions to users. The payment system 122 allows users to accumulatevalue (e.g., in a commercial currency, such as the U.S. dollar, or aproprietary currency, such as “points”) in accounts, and then later toredeem the accumulated value for products (e.g., goods or services) thatare made available via the publication system 120. The payment system122 also facilitates payments from a payment mechanism (e.g., a bankaccount or credit card) for purchases of items via the network-basedmarketplace. While the publication system 120 and the payment system 122are shown in FIG. 1 to both form part of the networked system 102, itwill be appreciated that, in alternative embodiments, the payment system122 may form part of a payment service that is separate and distinctfrom the networked system 102.

FIG. 1 also illustrates a third party module 128, executing on a thirdparty server 130, as having programmatic access through the network 104to the networked system 102 via the programmatic interface provided bythe API server 114. For example, the third party module 128 may,utilizing information retrieved from the networked system 102, supportone or more features or functions on a website (not shown) hosted by thethird party. The third party website may, for example, provide one ormore promotional, marketplace, or payment functions that are supportedby the relevant applications of the networked system 102.

While the network architecture 100 of FIG. 1 employs a client-serverarchitecture, a skilled artisan will recognize that the presentdisclosure is not limited to such an architecture. The networkarchitecture 100 can equally well find application in, for example, adistributed or peer-to-peer architecture system. The publication system120 and payment system 122 may also be implemented as standalone systemsor standalone software programs operating under separate hardwareplatforms, which do not necessarily have networking capabilities.

Referring now to FIG. 2, an example block diagram illustrating multiplecomponents that, in one embodiment, are provided within the publicationsystem 120 of the networked system 102 is shown. The publication system120 may be hosted on dedicated or shared server machines (not shown)that are communicatively coupled to enable communications between theserver machines. The multiple components themselves are communicativelycoupled (e.g., via appropriate interfaces), either directly orindirectly, to each other and to various data sources, to allowinformation to be passed between the components or to allow thecomponents to share and access common data. Furthermore, the componentsmay access the one or more database(s) 126 via the one or more databaseservers 124, both shown in FIG. 1.

The networked system 102 provides a number of publishing, listing, andprice-setting mechanisms whereby a seller may list (or publishinformation concerning) goods or services for sale, a buyer can expressinterest in or indicate a desire to purchase such goods or services, anda price can be set for a transaction pertaining to the goods orservices. To this end, the publication system 120 may comprise at leastone publication engine 202 and one or more auction engines 204 thatsupport auction-format listing and price setting mechanisms (e.g.,English, Dutch, Chinese, Double, Reverse auctions, etc.). The variousauction engines 204 also provide a number of features in support ofthese auction-format listings, such as a reserve price feature whereby aseller may specify a reserve price in connection with a listing and aproxy-bidding feature whereby a bidder may invoke automated proxybidding.

A pricing engine 206 supports various price listing formats. One suchformat is a fixed-price listing format (e.g., the traditional classifiedadvertisement-type listing or a catalogue listing). Another formatcomprises a buyout-type listing. Buyout-type listings (e.g., theBuy-It-Now (BIN) technology developed by eBay Inc., of San Jose, Calif.)may be offered in conjunction with auction-format listings and allow abuyer to purchase goods or services, which are also being offered forsale via an auction, for a fixed-price that is typically higher than astarting price of an auction for an item.

A store engine 208 allows a seller to group listings within a “virtual”store, which may be branded and otherwise personalized by and for theseller. Such a virtual store may also offer promotions, incentives, andfeatures that are specific and personalized to the seller. In oneexample, the seller may offer a plurality of items as Buy-It-Now itemsin the virtual store, offer a plurality of items for auction, or acombination of both.

A reputation engine 210 allows users that transact, utilizing thenetworked system 102, to establish, build, and maintain reputations.These reputations may be made available and published to potentialtrading partners. Because the networked system 102 supportsperson-to-person trading between unknown entities, users may otherwisehave no history or other reference information whereby thetrustworthiness and credibility of potential trading partners may beassessed. The reputation engine 210 allows a user, for example throughfeedback provided by one or more other transaction partners, toestablish a reputation within the networked system 102 over time. Otherpotential trading partners may then reference the reputation forpurposes of assessing credibility and trustworthiness.

Navigation of the network-based marketplace may be facilitated by anavigation engine 212. For example, a search module of the navigationengine 212 enables keyword searches of item listings published via thepublication system 120. In a further example, a browser module of thenavigation engine 212 allows users to browse various category,catalogue, or inventory data structures according to which listings maybe classified within the publication system 120. Various othernavigation applications within the navigation engine 212 may be providedto supplement the searching and browsing applications.

In order to make listings available via the networked system 102 asvisually informing and attractive as possible, the publication system120 may include an imaging engine 214 that enables users to uploadimages for inclusion within publications (e.g., listings) and toincorporate images within viewed listings. The imaging engine 214 alsoreceives image data from a user and utilizes the image data to identifyan item depicted or described by the image data. In some embodiments,the imaging engine 214 may receive images representing gesture inputsfrom the client device.

A listing creation engine 216 allows sellers to conveniently authorpublications in the example form of listings pertaining to goods orservices that sellers wish to transact via the networked system 102,while a listing management engine 218 allows sellers to manage suchlistings. Specifically, where a particular seller has authored orpublished a large number of listings, the management of such listingsmay present a challenge. The listing management engine 218 provides anumber of features (e.g., auto-relisting, inventory level monitors,etc.) to assist the seller in managing such listings.

A post-listing management engine 220 also assists sellers with a numberof activities that typically occur post-listing. For example, uponcompletion of an auction facilitated by the one or more auction engines204, a seller may wish to leave feedback regarding a particular buyer.To this end, the post-listing management engine 220 provides aninterface to the reputation engine 210 allowing the seller toconveniently provide feedback regarding multiple buyers to thereputation engine 210.

A messaging engine 222 is responsible for the generation and delivery ofmessages to users of the networked system 102. Such messages include,for example, advising users regarding the status of listings and bestoffers (e.g., providing an acceptance notice to a buyer who made a bestoffer to a seller). The messaging engine 222 may utilize any one of anumber of message delivery networks and platforms to deliver messages tousers. For example, the messaging engine 222 may deliver electronic mail(e-mail), an instant message (IM), a Short Message Service (SMS), text,facsimile, or voice (e.g., Voice over IP (VoIP)) messages via wirednetworks (e.g., the Internet), a Plain Old Telephone Service (POTS)network, or wireless networks (e.g., mobile, cellular, WiFi, WiMAX).

A gesture engine 224 manages receipt and processing of gesture inputsreceived from a client device (e.g., client device 110). The gestureengine 224 will be discussed in more detail in connection with FIG. 3.

An execution engine 226 manages execution of commands provided via thegesture input. The execution engine 226 will be discussed in more detailin FIG. 4.

Although the various components of the publication system 120 have beendefined in terms of a variety of individual modules and engines, askilled artisan will recognize that many of the items can be combined ororganized in other ways. Furthermore, not all components of thepublication system 120 have been included in FIG. 2. In general,components, protocols, structures, and techniques not directly relatedto functions of example embodiments (e.g., dispute resolution engine,loyalty promotion engine, personalization engines, etc.) have not beenshown or discussed in detail. The description given herein simplyprovides a variety of example embodiments to aid the reader in anunderstanding of the systems and methods used herein.

Application of Embodiments of the Gesture Function Platform into theExample Network Architecture

Referring now to FIG. 3, an example diagram of the gesture engine 224 isshown. The gesture engine 224 receives and processes gesture inputreceived from a client device (e.g., client device 110). In exampleembodiment, the gesture engine 224 comprises a gesture input module 302,a gesture identification module 304, a notification module 306, agesture training module 308, and a gesture application module 310.Alternative embodiments may comprise further components or modules.Furthermore, some of the components of the gesture engine 224 may belocated elsewhere (e.g., in the execution engine 226 or the messagingengine 222) or be combined into a single module.

In example embodiments, a user at the client device may search for orbrowse for an item of interest on the network-based marketplace. Basedon the search or browse, a listing or other type of publicationpertaining to the item of interest is presented to the user on a displayof the client device. The user may then indicate a commerce-relatedaction with respect to the item of interest. In some embodiments, theclient device may comprise a touch-sensitive display. In theseembodiments, the user may indicate the commerce-related action by“writing” an indication or symbol representative of the commerce-relatedaction on the touch-sensitive display as will be discussed furtherbelow. Other forms of gestures may be also be utilized.

The gesture input module 302 receives a gesture input from the clientdevice that represents a commerce-related action. In exampleembodiments, the gesture input is received at the client device via theuser physically interacting with a user interface presented on thetouch-sensitive display or using a mouse to input a gesture via a userinterface presented on the client device. In one embodiment, the gestureinput is a set of coordinates that represent a gesture. The set ofcoordinates may represent a letter that symbolizes an action a user atthe client device wants to perform. For example, the set of coordinatesmay represent a “B” for a buy action, “S” for a sell action, “P” for apay action, or “W” for a watch action. Other letters or symbols (e.g.,“$” for a pay action or “+” to add to a shopping cart) may be used torepresent other actions that may be used in connection with thenetwork-based marketplace. Alternatively, other letters or symbols maybe used to represent actions for other networked environments.

In another embodiment, the gesture input module 302 receives a gestureinput that is a motion of a client device. In some embodiments, a motionsensor may be coupled to, or otherwise be embedded within the clientdevice to detect the motion. For example, the gesture input may be ashaking motion (e.g., the client device is shaken). The shaking motionmay, in one embodiment, cause a refresh or update action to occur. Anyaction that may be performed on or to the client device may be used as agesture input.

The gesture identification module 304 identifies the gesture inputreceived by the gesture input module 302. In some embodiments, adatabase (e.g., database 126) of known gestures may be referenced todetermine a match between the known gestures and the gesture input. Adegree of tolerance may be factored in to account for slight differencebetween the known gestures and the gesture input (e.g., writing styledifferences). In embodiments where the gesture is the set ofcoordinates, the gesture identification module 304 analyzes the set ofcoordinates to determine the action associated with the set ofcoordinates. For example, the gesture identification module 304 maydetermine that the set of coordinates represent a “B” which indicatesthe user's desire to buy an item represented on their client device uponwhich the “B” motion was written. While capital letters are used todescribe example embodiments, it should be noted that the capitalletters and lower case letters may be used interchangeable in exampleembodiments. Thus for example, while “B” is used to describe a buycommerce-related action, “b” can equally be used. In addition, symbolsmay be used to represent the commerce-related action. For example, “S”may be used to represent a pay request action.

In embodiments where in the gesture input is a motion of a device (oraccessory coupled to a device, such as a cursor or UI controller), thegesture identification module 304 identifies the motion and converts themotion to an action. In some cases, the motion may be a shake of theclient device which may indicate a refresh request. In other cases, themotion may be a side-way motion or a forward-backward motion whichrepresents other actions (e.g., update request, last page, next page).

In some embodiments, the gesture identification module 304 may notrecognize the gesture input. In these embodiments, the notificationmodule 306 generates a notice to the user that the gesture input is notrecognized. The notice may request that the user re-enter the gesture oruse a different manner of providing a gesture input or provide a generalinput (e.g., use a cursor or keyboard). The notification module 306 thentransmits the notice or provides the notice to the messaging engine 222for transmission.

The gesture training module 308 learns new gestures or slightmodifications to existing gestures. For example, a user of the clientdevice may swipe a letter “B” in a script motion resulting in a “B” thatappears like “

.” The gesture training module 308 learns style differences presented bythe user. As a result, the gesture engine 224 is more likely torecognize the style differences in the future.

The gesture application module 310 provides an application to the clientdevice that allows the client device to provide gesture functions. Thegesture application provides instructions to the client device in orderfor the client device to capture gesture inputs.

In alternative embodiments, the instructions provided by the gestureapplication module 310 also instruct the client device to convert agesture input into a set of coordinates that represent the gestureinput. In these cases, the client device may comprise a gesture databasewhich is used to identify the commerce-related action based on thegesture input. The commerce-related action is then transmitted (as agesture input) to the execution engine 226. Thus, the gesture input maybe converted at the client device instead of at the publication system120. Therefore, some of the modules of the gesture engine 224 may, inalternative embodiments, be located at the client device.

Referring now to FIG. 4, an example diagram of the execution engine 226is shown. The execution engine 226 manages the execution of actions thatare represented by the gesture inputs. In example embodiments, once thegesture input is identified by the gesture identification module 304 andthe corresponding action request is determined, the action request issent to the execution engine 226 for processing. The execution engine226 comprises an action determination module 402, a notification module404, and an action execution module 406. Alternative embodiments mayprovide functionally equivalent components in more or less modules.Furthermore, some of the components of the execution engine 226 may belocated elsewhere (e.g., in the gesture engine 224) or combined into asingle module.

The action determination module 402 determines whether the actionrequest received from the gesture identification module 304 isexecutable. In one embodiment, this determination is based on whetherthe commerce-related action is compatible with a status of the item ofinterest. For example, if the gesture input indicated a request to buyan item represented by the listing that the buy gesture input wasindicated upon but the item has already been sold, then the actiondetermination module 402 concludes that the action cannot be performed.Other statuses may include, for example, watching, no longer for sale,receiving bids, auction expired, and Buy-It-Now item.

The notification module 404 of the execution engine 226 manages noticesto a user based on actions or non-actions of the execution engine 226.Thus, if the action determination module 402 determines that an actionrequest cannot be performed, then the notification module 404 generatesa notice to the user reporting the same. In embodiments where the actioncan be performed, the notification module 404 may generate a notice tothe user upon execution of the action request. It should be noted thatthe notification module 306 of the gesture engine 224 and thenotification module 404 of the execution engine 226 may be combined intoa single notification module. Furthermore, the notification module 306may transmit the notice or provides the notice to the messaging engine222 for transmission.

The action execution module 406 performs the commerce-related action. Inembodiments where the commerce-related action is to buy an item, theaction execution module 406 initiates a purchase transaction.Conversely, if the commerce-related action is to sell an item, then theaction execution module 406 initiates a sales transaction. The salestransaction may include generating and posting a listing for the item onthe network-based marketplace. Alternatively, the sales transaction maybe in response to an offer to buy in which case, the sales transactioncompletes the sale (e.g., accept the offer, close the listing for theitem, and send a payment request to buyer). If the commerce-relatedaction is to watch an item, then the action execution module 406 placesthe item into a watch list associated with the user. A commerce-relatedaction to pay triggers a payment transaction. In one embodiment, thepayment transaction may be an automatic transfer of funds to the seller.In an alternative embodiment, the payment transaction may trigger apayment interface whereby the user may enter payment information orverify pre-populated payment information.

While the gesture engine 224 and the execution engine 226 are shown asbeing a part of the publication system 120, it should be noted that oneor more of the modules of the gesture engine 224 and the executionengine 226 may be located at the client device. That is, some of thefunctionality may be provided, in part, by the client device.

FIG. 5 is a flowchart illustrating a method 500 to provide gesturefunctions at a client device. At operation 502, display instructions forproviding an interface on the client device is rendered and transmitted.In some embodiments, the imaging engine 214 in connection with theauction engines 204 provides information regarding items available viathe network-based marketplace. In one example, the information maycomprise one or more item listings whereby each item listing representsan item available for purchase or auction. The information may bedetermined in response to a search or browsing for items of interestperformed by the user at the client device. The display instructions arereceived by the client device and displayed to the user.

In response, the user may decide to perform an action with respect toinformation (e.g., a publication or listing) provided by the displayinstructions. In various embodiments, the user may, for example, sell,buy, watch, or pay for an item represented by the information. In otherembodiments, the user may request an update to the information. Forexample, the user may monitor an auction for an item, and request anupdate in order to check if new bid offers have been submitted since thelast update or receipt of information.

The user provides a gesture input on their client device which reflectsthe action they desire to perform. Thus, the user may draw a letter(e.g., S, B, W, P) or symbol (e.g., $, +) on a touch-sensitive displayof the client device. Alternatively, the user may shake the clientdevice or move the client device in a particular motion. The gestureinput is received at operation 504. In example embodiments, the gestureinput module 302 receives the gesture input.

At operation 506, a determination is made as to whether the gestureinput is recognized as representing an action request. In exampleembodiments, the gesture identification module 304 performs thedetermination. In one embodiment, the gesture identification module 304may access a database of known gesture inputs and compares the receivedgesture input to the known gesture inputs.

If a no match is found, then a notification is sent at operation 508.The notification informs the user that the gesture input isunrecognizable and may request the user to re-enter the gesture input.Alternatively, the user may be requested to provide the action requestusing a different gesture input method or general input method (e.g.,use a cursor or keyboard).

If at operation 506, the gesture input is recognized, then at operation510, a further determination is made as to whether the commerce-relatedaction is executable (e.g., compatible with a status of the item ofinterest). If the commerce-related action is not executable, anotification to that effect is sent at operation 508. However, if theaction is executable, then the action is performed at operation 512.

FIG. 6a illustrates an example of a gesture input at a client device600. The client device 600 comprises a display area 602 whereininformation from the network-based marketplace may be displayed. Theinformation may be arrived at via a search on the network-basedmarketplace or via browsing the network-based marketplace. In thepresent example, a user of the client device 600 is interested in buyingan item illustrated in the display area. As such, the user may indicateon a touch-sensitive display of the client device 600 their desire tobuy the item.

Moving from FIG. 6a to FIG. 6b , the user has drawn a letter “B” on thetouch-sensitive display of the client device 600. The “B” indicates adesire to buy the item (e.g., “Buy it Now” item) or “B” may indicate adesire to place a bid on the item if the item is up for auction.

FIG. 7a and FIG. 7b illustrate more examples of gesture inputs at aclient device 700. These examples show a motion performed with theclient device 700 which may trigger an action with respect toinformation being displayed on the client device 700. As shown in FIG.7a , the client device 700 is moved in a forward-backward motion 702.Alternatively, FIG. 7b shows the client device 700 moved in a sidewaymotion 704. Other motions may be used. For example, the client device700 may be shaken.

Modules, Components, and Logic

Certain embodiments described herein may be implemented as logic or anumber of modules, engines, components, or mechanisms. A module, engine,logic, component, or mechanism (collectively referred to as a “module”)may be a tangible unit capable of performing certain operations andconfigured or arranged in a certain manner. In certain exampleembodiments, one or more computer systems (e.g., a standalone, client,or server computer system) or one or more components of a computersystem (e.g., a processor or a group of processors) may be configured bysoftware (e.g., an application or application portion) or firmware (notethat software and firmware can generally be used interchangeably hereinas is known by a skilled artisan) as a module that operates to performcertain operations described herein.

In various embodiments, a module may be implemented mechanically orelectronically. For example, a module may comprise dedicated circuitryor logic that is permanently configured (e.g., within a special-purposeprocessor, application specific integrated circuit (ASIC), or array) toperform certain operations. A module may also comprise programmablelogic or circuitry (e.g., as encompassed within a general-purposeprocessor or other programmable processor) that is temporarilyconfigured by software or firmware to perform certain operations. Itwill be appreciated that a decision to implement a module mechanically,in the dedicated and permanently configured circuitry, or in temporarilyconfigured circuitry (e.g., configured by software) may be driven by,for example, cost, time, energy-usage, and package size considerations.

Accordingly, the term module should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which modules orcomponents are temporarily configured (e.g., programmed), each of themodules or components need not be configured or instantiated at any oneinstance in time. For example, where the modules or components comprisea general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differentmodules at different times. Software may accordingly configure theprocessor to constitute a particular module at one instance of time andto constitute a different module at a different instance of time.

Modules can provide information to, and receive information from, othermodules. Accordingly, the described modules may be regarded as beingcommunicatively coupled. Where multiples of such modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe modules. In embodiments in which multiple modules are configured orinstantiated at different times, communications between such modules maybe achieved, for example, through the storage and retrieval ofinformation in memory structures to which the multiple modules haveaccess. For example, one module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further module may then, at a later time,access the memory device to retrieve and process the stored output.Modules may also initiate communications with input or output devicesand can operate on a resource (e.g., a collection of information).

Example Machine Architecture and Machine-Readable Medium

With reference to FIG. 8, an example embodiment extends to a machine inthe example form of a computer system 800 within which instructions forcausing the machine to perform any one or more of the methodologiesdiscussed herein may be executed. In alternative example embodiments,the machine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a network router, a switchor bridge, or any machine capable of executing instructions (sequentialor otherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The example computer system 800 may include a processor 802 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 804 and a static memory 806, which communicate witheach other via a bus 808. The computer system 800 may further include avideo display unit 810 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). In example embodiments, the computer system 800also includes one or more of an alpha-numeric input device 812 (e.g., akeyboard), a user interface (UI) navigation device or cursor controldevice 814 (e.g., a mouse), a disk drive unit 816, a signal generationdevice 818 (e.g., a speaker), and a network interface device 820.

Machine-Readable Medium

The disk drive unit 816 includes a machine-readable medium 822 on whichis stored one or more sets of instructions 824 and data structures(e.g., software instructions) embodying or used by any one or more ofthe methodologies or functions described herein. The instructions 824may also reside, completely or at least partially, within the mainmemory 804 or within the processor 802 during execution thereof by thecomputer system 800, the main memory 804 and the processor 802 alsoconstituting machine-readable media.

While the machine-readable medium 822 is shown in an example embodimentto be a single medium, the term “machine-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, or associated caches and servers) that store the one or moreinstructions. The term “machine-readable medium” shall also be taken toinclude any tangible medium that is capable of storing, encoding, orcarrying instructions for execution by the machine and that cause themachine to perform any one or more of the methodologies of embodimentsof the present invention, or that is capable of storing, encoding, orcarrying data structures used by or associated with such instructions.The term “machine-readable medium” shall accordingly be taken toinclude, but not be limited to, solid-state memories and optical andmagnetic media. Specific examples of machine-readable media includenon-volatile memory, including by way of example semiconductor memorydevices (e.g., Erasable Programmable Read-Only Memory (EPROM),Electrically Erasable Programmable Read-Only Memory (EEPROM), and flashmemory devices); magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Transmission Medium

The instructions 824 may further be transmitted or received over acommunications network 826 using a transmission medium via the networkinterface device 820 and utilizing any one of a number of well-knowntransfer protocols (e.g., HTTP). Examples of communication networksinclude a local area network (LAN), a wide area network (WAN), theInternet, mobile telephone networks, Plain Old Telephone (POTS)networks, and wireless data networks (e.g., WiFi and WiMax networks).The term “transmission medium” shall be taken to include any intangiblemedium that is capable of storing, encoding, or carrying instructionsfor execution by the machine, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader spirit and scope of embodiments of the present invention. Suchembodiments of the inventive subject matter may be referred to herein,individually or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any single invention or inventive concept if more thanone is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

Moreover, plural instances may be provided for resources, operations, orstructures described herein as a single instance. Additionally,boundaries between various resources, operations, modules, engines, anddata stores are somewhat arbitrary, and particular operations areillustrated in a context of specific illustrative configurations. Otherallocations of functionality are envisioned and may fall within a scopeof various embodiments of the present invention. In general, structuresand functionality presented as separate resources in the exampleconfigurations may be implemented as a combined structure or resource.Similarly, structures and functionality presented as a single resourcemay be implemented as separate resources. These and other variations,modifications, additions, and improvements fall within a scope ofembodiments of the present invention as represented by the appendedclaims. The specification and drawings are, accordingly, to be regardedin an illustrative rather than a restrictive sense.

What is claimed is:
 1. A method to provide gesture functionality, themethod comprising: receiving, by a computing device, a gesture input inrelation to a listing of an item; identifying, by the computing device,a style difference between a known gesture input of a set of knowngesture inputs and the received gesture input; learning, by thecomputing device, to recognize the received gesture input as the knowngesture input based on identifying the style difference; and causing, bythe computing device, an action that corresponds to the known gestureinput to be performed within a networked environment, performance of theaction being based on a compatibility between the action and a status ofthe listing of the item.
 2. The method as described in claim 1, furthercomprising causing modification of the set of known gesture inputs toinclude the style difference by updating a database that stores the setof known gesture inputs.
 3. The method as described in claim 1, whereinthe gesture input is received via a touch-sensitive display of thecomputing device.
 4. The method as described in claim 1, furthercomprising displaying the listing of the item and causing the action tobe performed in relation to the item.
 5. The method as described inclaim 1, wherein the received gesture input represents a symbol.
 6. Themethod as described in claim 1, wherein the received gesture inputrepresents a symbol which represents a commerce related action.
 7. Themethod as described in claim 1, wherein the received gesture input isreceived by receiving input associated with motion of the computingdevice.
 8. The method as described in claim 1, wherein the action thatcorresponds to the known gesture input is a commerce-related action tobe performed within the networked environment in relation to the item ofthe listing.
 9. The method as described in claim 1, wherein thenetworked environment includes a network-based marketplace and theaction that corresponds to the known gesture input is performed inrelation to the network-based marketplace.
 10. The method as describedin claim 1, wherein the known gesture input is a swiping gesture.
 11. Acomputing device comprising: at least one user interface to receive agesture input in relation to a listing of an item published by anetworked environment; and a gesture engine implemented at the computingdevice to: identify a style difference between a known gesture input ofa set of known gesture inputs and the received gesture input; learn torecognize the received gesture input as the known gesture input based onidentifying the style difference; and cause an action that correspondsto the known gesture input to be performed within the networkedenvironment, performance of the action being based on a compatibilitybetween the action and a status of the listing of the item.
 12. Thecomputing device as described in claim 11, further comprising a gesturedatabase to store the set of known gesture inputs.
 13. The computingdevice as described in claim 12, wherein the gesture engine is furtherconfigured to cause modification of the set of known gesture inputs toinclude the style difference by updating the gesture database.
 14. Thecomputing device as described in claim 11, wherein the at least one userinterface is a touch-sensitive display of the computing device.
 15. Thecomputing device as described in claim 11, wherein the at least one userinterface is further configured to cause display of the listing of theitem and cause the action to be performed in relation to the item. 16.The computing device as described in claim 11, wherein the receivedgesture input represents a symbol.
 17. The computing device as describedin claim 11, wherein the received gesture input represents a symbolwhich represents a commerce related action.
 18. One or morecomputer-readable storage media having stored thereon instructions thatare executable by a computing device to perform operations comprising:receiving a gesture input in relation to a listing of an item publishedby a networked environment; identifying a style difference between aknown gesture input of a set of known gesture inputs and the receivedgesture input; learning to recognize the received gesture input as theknown gesture input based on identifying the style difference; andcausing an action that corresponds to the known gesture input to beperformed within the networked environment, performance of the actionbeing based on a compatibility between the action and a status of thelisting of the item.
 19. The one or more computer-readable storage mediaas described in claim 18, wherein the gesture input is received via atouch-sensitive display of the computing device.
 20. The one or morecomputer-readable storage media as described in claim 18, wherein theoperations further comprise displaying the listing of the item andcausing the action to be performed in relation to the item.